"Network handshaking," which involves layer 1/2/3 connectivity and compatibility. These are the first steps when troubleshooting issues in high-bandwidth IP-based systems.
These are common foundational checks because mismatches here prevent proper link establishment, packet exchange, or reliable high-throughput communication before you even get to higher-level issues like multicast, PTP timing, IGMP, or flow configuration in ST 2110.
| What (Action) | Where (Location) | Why (Rationale) |
|---|---|---|
|
Set MTU to 9000
Many 10G+ networks (including ST 2110 deployments) benefit from or require jumbo frames for efficiency and to avoid fragmentation on large video packets. Standard Ethernet MTU is 1500; 9000 is typical for jumbo. However, it must be set consistently end-to-end (NICs, switches, routers, SFPs/interfaces). Inconsistent MTU is a very common cause of "connects but doesn't work well" or intermittent failures. Test it properly with large pings (e.g., ping -M do -s 8972
Jumbo Frames Why? Must Know! |
All devices
• Network Interface Cards (NICs) – Endpoints
along the entire path must support and be configured with a consistent MTU (typically 9000 on end devices, often 9216 on switches for headroom with VLAN tags or other encapsulation).* Windows: Device Manager → Network adapters → Properties → Advanced → Jumbo Frame (or MTU) → set to 9000 (or "9K" / "9014" depending on the driver). * Alternatively, use PowerShell: Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Jumbo Packet" -DisplayValue "9014 Bytes". * Linux: sudo ip link set dev eth0 mtu 9000 (or use ethtool / network manager). Make it persistent in /etc/network/interfaces or netplan. • Network Switches (Core of the 2110 Fabric) * Arista EOS: Primarily CLI (most reliable for media networks):interface Ethernet1 mtu 9216 (or global: mtu 9000 for Layer 3 interfaces). Web GUI exists but is less commonly used for deep config in 2110 setups. * Cisco Nexus / Catalyst: CLI (NX-OS): interface Ethernet1/1 mtu 9216, Or system-wide: system jumbomtu 9216 Some models have a basic web GUI or DCNM (Data Center Network Manager) for graphical configuration, but CLI is standard for production 2110. * Mellanox/NVIDIA: Web GUI (Onyx or Cumulus Linux) — often the easiest for smaller setups. Go to Switch > Interfaces or System > MTU and set jumbo frame size. CLI also available. * NETGEAR M4350 / AV switches: Web GUI is user-friendly and purpose-built for AV-over-IP / ST 2110. Look under Switching > Ports > Advanced or Jumbo Frames settings. Other managed switches (e.g., Edgecore, Aruba): Web interface (usually under Port Configuration > Advanced or Jumbo Frame / MTU section). CLI for scripting/automation. Best practice: Enable jumbo frames on the specific VLAN used for ST 2110 traffic (often an isolated media VLAN) rather than globally, to avoid issues with management traffic. Generic Setup panel |
Prevents 2110-20 video packets from fragmenting, reducing CPU overhead and packet loss. Why? |
|
Assign Static IPs
Highly recommended. DHCP can introduce delays, lease issues, or conflicts in controlled environments like media networks or storage fabrics. Static IPs with proper subnet/gateway ensure predictable addressing. In ST 2110 troubleshooting guides, this is often explicitly advised (along with verifying subnet mask and no gateway if it's a isolated media VLAN). Dynamic addressing can cause "no link" or flow discovery problems.
DHCP IP Addressing Private IPs IPv4 CIDR Range Calculator |
Static IPs must be set on
every device
• Network Interface Cards (
NICs
) on Endpoints
that participates in the 2110 traffic (senders, receivers, and sometimes control/management interfaces). The management network (for GUIs and NMOS) may use DHCP or static separately.
* Windows-based devices (many media cards): Windows Network Settings → Adapter Properties → IPv4 → Use the following IP address → enter IP, Subnet Mask (usually 255.255.255.0), Gateway (often none or management gateway), DNS. For some cards (e.g., Matrox X.mio5), you may also edit an ipconfig.xml file for additional PTP/media interfaces. •Linux-based devices (common in servers/gateways): sudo ip addr add <IP>/<mask> dev eth0 (temporary) or edit netplan / /etc/network/interfaces for persistence. Many also support ethtool or vendor tools. Dedicated hardware endpoints: Via the device's own web GUI (connect via temporary DHCP or direct cable first). •IP Gateways, Converters, and Specialized Media Devices These often have dual interfaces (media + management). Common examples and GUIs: Matrox, AJA, Embrionix, Lawo, Riedel, Hitomi MatchBox, EEG Alta, Haivision, etc.: Web browser interface (HTTP/HTTPS on the management port). Look for sections like: Network, System > Network & Time, Interfaces, IP Configuration, or ST 2110 Page. Choose Static mode, enter IP address, subnet, gateway. Some require separate IPs per SFP/port (e.g., one for PTP, one for essence in IGMPv3 setups). Many support NMOS IS-04/IS-05 configuration in the same GUI (for discovery and routing), with options for static registry IP if mDNS is disabled. • Network Switches (Rarely Need Static IP on Media Ports) Switches themselves usually get a management IP (static recommended for reliable access). Media ports in a pure Layer 2 2110 fabric typically do not need individual IPs — multicast traffic flows without them. * Common switches in 2110: Arista (most popular): Primarily CLI (interface VlanX or management interface → ip address <IP> <mask>). Web GUI exists but is secondary. Cisco Nexus: CLI (NX-OS) or DCNM (Data Center Network Manager) GUI. NVIDIA/Mellanox (SN series): Web GUI (Onyx/Cumulus) under System > Management or Interfaces. CLI also available. NETGEAR M4350 (AV-friendly): User-friendly Web GUI → look under IP Configuration, Management, or System > Management IP. For switches, set the management VLAN /IP statically so you can always reach the GUI/CLI even if the media network is isolated. • NMOS Controllers / Registry (Discovery & Control Layer) NMOS (IS-04 for discovery, IS-05 for routing) is widely used in 2110 systems. NMOS Registry (e.g., open-source or vendor like Sony, AWS Elemental, or integrated in controllers): Static IP on the server/VM running the registry. Configured via its web UI or config files. Many devices then point to this static registry IP instead of relying on mDNS. Orchestration tools (Imagine Magellan, Grass Valley Orbit, Arista MCS, etc.): Static IPs for the controller servers. Best Practices for Static IP in 2110 * Use a dedicated media VLAN (isolated from corporate/IT traffic). * Document all IPs clearly (spreadsheet is common). * No gateway on pure media interfaces in many isolated setups (prevents accidental routing). * For redundancy (2022-7), ensure primary/secondary interfaces have distinct static IPs on separate networks. * Test with ping and large-packet tests after changes. * Combine with static multicast addresses for flows. Verification: After setting static IPs, use tools like ping, ethtool, switch show interfaces, or NMOS explorers to confirm devices register and flows connect reliably. If you're working with a specific device or switch model (e.g., Arista 7280, Matrox, AJA, NETGEAR M4350, Lawo, etc.), tell me the exact hardware and I can give more precise GUI navigation or CLI commands. |
In a SMPTE ST 2110 system, assigning static IPs (instead of DHCP) is a strongly recommended best practice. DHCP can introduce delays, lease renewals, or conflicts that disrupt real-time media flows, PTP timing, and redundancy (e.g., ST 2022-7). Static addressing ensures predictable, stable connectivity for all devices on the media network (often an isolated VLAN). |
|
Verify SFP Speed
Critical. SFPs must match the port speed (e.g., 10G SFP+ in a 10G port, not a 1G SFP), transceiver type (SR vs LR), cable (fiber multimode/singlemode, DAC, etc.), and both ends. Mismatch leads to no link, wrong negotiated speed, or unstable connection. Check with tools like ethtool (Linux) for actual link speed/duplex, or switch CLI (show interfaces transceiver). Also verify SFP insertion, LEDs, and compatibility with your switch/NIC (some ports are speed-locked).
Study Plan |
Physical Port / Switch CLI | SDI-to-IP gateways'
SFPs
SFP stands for Small Form-factor Pluggable. It is a compact, hot-swappable transceiver module used in network switches, NICs, gateways, and media devices to provide high-speed Ethernet connectivity.
require symmetric bandwidth (e.g., 25G) to prevent buffer overflows during uncompressed bursts.
In SMPTE ST 2110 systems, SFPs are the physical interfaces that connect devices to the IP network for transporting uncompressed (or lightly compressed) video (2110-20), audio (2110-30), and data (2110-40) streams. Why SFP matters in 2110: • Most 2110 endpoints and switches use SFP+ or SFP28 cages instead of fixed RJ-45 ports. • They allow flexible choice of media: multimode fiber (short distance), single-mode fiber (long distance), or Direct Attach Copper (DAC) cables. • Speed matching is critical — a mismatch (e.g., putting a 1G SFP in a 10G port) prevents link establishment. Common SFP Types in ST 2110 Deployments: • 10G SFP+ — Most common for standard 2110 video flows (e.g., 1080p/4K uncompressed). • 25G SFP28 — Used for higher bandwidth needs (UHD, multiple flows per port, or headroom). • SR (Short Reach) — Multimode fiber, up to ~300m, cheaper optics. • LR (Long Reach) — Single-mode fiber, up to 10km+. • DAC (Direct Attach Copper) — Short, low-cost copper cables (1–5m) between devices and switches. Specialized 2110 SFPs: Some manufacturers (Embrionix/emSFP, Artel, Analog Way, Riedel MuoN, etc.) offer “smart” or software-defined SFPs that include built-in ST 2110 gateway functionality — they can convert SDI directly to IP (or vice versa) inside the SFP itself. Best Practice: Always verify both ends use compatible SFPs (same speed, same fiber type, same wavelength). Check with ethtool -m on Linux or the switch CLI (show interfaces transceiver).Mismatched or incompatible SFPs are one of the most common causes of “no link” or unstable connections in 2110 systems. |
